CTAL-ATT: Certified Tester Advanced Level Agile Technical Tester

What are the characteristics of a unit test that are defined with the acronym FIRST?

Fast, Iterative, Replaceable, Stable, Tolerant
Fast, Isolated, Repeatable, Self-validating, Thorough
Fast, Implemented, Recorded, Source-controlled, Tactical
Fast, Immediate, Relevant, Standardized, Transparent

Correct answer: B

Explanation:

FIRST Acronym in Unit Testing:Fast: Unit tests should execute quickly.Isolated: They should run independently of other tests.Repeatable: Tests should yield consistent results under the same conditions.Self-validating: Results should indicate a pass or fail automatically.Thorough: Each test should comprehensively cover the targeted functionality.Analyzing the Options: A: Incorrect terms such as 'Iterative' and 'Tolerant' are unrelated to unit tests.C: Includes terms like 'Recorded' and 'Source-controlled,' which do not align with FIRST.D: Terms like 'Immediate' and 'Transparent' are unrelated to unit testing principles.Aligned with ISTQB Agile Technical Tester syllabus defining unit test characteristics using the FIRST acronym.

FIRST Acronym in Unit Testing:

Fast: Unit tests should execute quickly.

Isolated: They should run independently of other tests.

Repeatable: Tests should yield consistent results under the same conditions.

Self-validating: Results should indicate a pass or fail automatically.

Thorough: Each test should comprehensively cover the targeted functionality.

Analyzing the Options:

A: Incorrect terms such as 'Iterative' and 'Tolerant' are unrelated to unit tests.

C: Includes terms like 'Recorded' and 'Source-controlled,' which do not align with FIRST.

D: Terms like 'Immediate' and 'Transparent' are unrelated to unit testing principles.

Aligned with ISTQB Agile Technical Tester syllabus defining unit test characteristics using the FIRST acronym.

You are testing a mission-critical system and want to use exploratory testing for part of the testing. According to the syllabus, what is the correlation between this type of testing and the risk level of the item being tested?

High = recommended, Medium = recommended, Low = highly recommended
High = recommended, Medium = highly recommended, Low = highly recommended
High = highly recommended, Medium = highly recommended, Low = highly recommended
High = not recommended, Medium = recommended, Low = highly recommended

Correct answer: C

Explanation:

Exploratory Testing and Risk Levels:Exploratory testing is a flexible approach that involves simultaneous test design and execution, making it highly valuable across all risk levels.For high-risk systems, exploratory testing is essential as it uncovers critical issues efficiently.For medium- and low-risk systems, it is equally beneficial for identifying functional and usability defects, especially when formal test cases may not cover all scenarios.Analyzing the Options:A and B: These fail to emphasize the importance of exploratory testing for high-risk systems.D: States that exploratory testing is 'not recommended' for high-risk systems, which is inaccurate.C: Correctly states that exploratory testing is 'highly recommended' across all risk levels, aligning with the ISTQB syllabus guidance.ISTQB Advanced Agile Technical Tester syllabus highlights exploratory testing as a versatile and valuable technique for all risk levels.

Exploratory Testing and Risk Levels:

Exploratory testing is a flexible approach that involves simultaneous test design and execution, making it highly valuable across all risk levels.

For high-risk systems, exploratory testing is essential as it uncovers critical issues efficiently.

For medium- and low-risk systems, it is equally beneficial for identifying functional and usability defects, especially when formal test cases may not cover all scenarios.

Analyzing the Options:

A and B: These fail to emphasize the importance of exploratory testing for high-risk systems.

D: States that exploratory testing is 'not recommended' for high-risk systems, which is inaccurate.

C: Correctly states that exploratory testing is 'highly recommended' across all risk levels, aligning with the ISTQB syllabus guidance.

ISTQB Advanced Agile Technical Tester syllabus highlights exploratory testing as a versatile and valuable technique for all risk levels.

You are testing a new feature in the current iteration. The feature is supposed to take the input of a name and return the number of characters in the name. This information is used by another feature that will determine the size needed on a form. The acceptance criteria state the following

1) a name of up to 30 characters should be accepted

2) standard error processing should be in place to limit user errors

The developers are using TDD and you have asked to see their tests. This is what they gave you

When you run your manual tests you are finding that when you use the following inputs you get the associated results:

From these results what can you conclude about the TDD process?

The developers are not running the tests prior to releasing the code
The tests cannot be passing
The tests are insufficient and need to include more options
The story needs to be enhanced to include the capabilities that are causing errors

Correct answer: C

Explanation:

The TDD process, as described, seems to lack comprehensive testing that covers all the acceptance criteria. Specifically, the tests provided by the developers do not address the full range of input validation, such as ensuring that names with up to 30 characters are accepted and that standard error processing is in place to limit user errors. This indicates that the tests are insufficient and need to include more options to fully validate the feature against its acceptance criteria.The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of creating testable acceptance criteria within an Agile team and implementing various Agile test approaches using appropriate techniques12.It also highlights the need for supporting and contributing to test automation activities in an Agile project12, which includes ensuring that all acceptance criteria are met and that tests are sufficiently robust to catch potential errors.ISTQB Advanced Level Agile Technical Tester Syllabus1ISTQB Advanced Level Agile Technical Tester Learning Objectives2

The TDD process, as described, seems to lack comprehensive testing that covers all the acceptance criteria. Specifically, the tests provided by the developers do not address the full range of input validation, such as ensuring that names with up to 30 characters are accepted and that standard error processing is in place to limit user errors. This indicates that the tests are insufficient and need to include more options to fully validate the feature against its acceptance criteria.The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of creating testable acceptance criteria within an Agile team and implementing various Agile test approaches using appropriate techniques12.It also highlights the need for supporting and contributing to test automation activities in an Agile project12, which includes ensuring that all acceptance criteria are met and that tests are sufficiently robust to catch potential errors.

ISTQB Advanced Level Agile Technical Tester Syllabus1

ISTQB Advanced Level Agile Technical Tester Learning Objectives2

You have been given the following story

As a shopper

I want to scan my membership card

So that I get all the discounts I'm entitled to receive

Which of the following is the correct use of BDD to design test scenarios?

Given that the shopper scans their card When they checkout Then they should receive alt the quantity discounts for everything they have purchased
As a store clerk I want to scan a customer's card So that their total includes their discounts
Given that I have scanned my card I expect to receive my discounts And an itemized list of what I bought
Given that a card is scanned Then discounts should be applied When the customer checks out

Correct answer: A

Explanation:

The correct use of Behavior-Driven Development (BDD) to design test scenarios involves specifying the behavior in a given-when-then format. This format helps to clarify the conditions under which a particular outcome should occur. Option A follows this structure correctly:Giventhat the shopper scans their card (the precondition),Whenthey checkout (the action),Thenthey should receive all the quantity discounts for everything they have purchased (the expected outcome).This scenario clearly outlines the behavior of the system in response to the user's actions, which is central to BDD.Reference= The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of creating testable acceptance criteria for a given user story using requirements engineering and test techniques, which include the application of BDD in the context of a given user story12.

The correct use of Behavior-Driven Development (BDD) to design test scenarios involves specifying the behavior in a given-when-then format. This format helps to clarify the conditions under which a particular outcome should occur. Option A follows this structure correctly:

Giventhat the shopper scans their card (the precondition),

Whenthey checkout (the action),

Thenthey should receive all the quantity discounts for everything they have purchased (the expected outcome).

This scenario clearly outlines the behavior of the system in response to the user's actions, which is central to BDD.

Reference= The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of creating testable acceptance criteria for a given user story using requirements engineering and test techniques, which include the application of BDD in the context of a given user story12.

You have received this BDD test

Given that a customer enters the correct PIN When they request to make a withdrawal And they have enough money in their account Then they will receive the money And a receipt

Which of the following is the user story that best fits this BDD test?

As a customer I want to deposit money into my account So that I can collect interest
As an ATM I want to provide services to my customer So they will be happy
As a customer I want to withdraw money from my account So that I can buy a present
As a bank teller I want customers to use the ATM So that I don't have to deal with them

Correct answer: C

Explanation:

The BDD test scenario provided describes a customer performing a withdrawal transaction after entering the correct PIN and having sufficient funds in their account. The outcome is the customer receiving money and a receipt. This aligns with the user story in option C, which focuses on the customer's desire to withdraw money for a specific purpose, which is to buy a present. The other options do not match the actions described in the BDD test scenario.Reference= The answer is verified based on the ISTQB Advanced Level Agile Technical Tester documents which emphasize the importance of aligning BDD scenarios with the corresponding user stories to ensure that the tests reflect the user's needs and interactions with the system12.

The BDD test scenario provided describes a customer performing a withdrawal transaction after entering the correct PIN and having sufficient funds in their account. The outcome is the customer receiving money and a receipt. This aligns with the user story in option C, which focuses on the customer's desire to withdraw money for a specific purpose, which is to buy a present. The other options do not match the actions described in the BDD test scenario.

Reference= The answer is verified based on the ISTQB Advanced Level Agile Technical Tester documents which emphasize the importance of aligning BDD scenarios with the corresponding user stories to ensure that the tests reflect the user's needs and interactions with the system12.

You have been working as a tester in an Agile team You have found that the user stories are being defined by the team but it is still unclear what will be a successful outcome Even after story elaboration you are still unclear as to what a story should do As a result, you're not really sure what to test or to know when you'll be done with testing This problem is becoming worse as completed stories are showcased but the product owner is unhappy with the results

You've looked into the matter further and the comments from the product owner indicate that features are missing from the stories. The story is functioning correctly within the limited definition of the story but the product owner is expecting more functionality, such as error handling that isn't being defined in the story

What technique should you implement that would help to further define the product owner's expectations and alleviate the issues that are arising during the show cases?

TDD by the developers before they begin coding
BDD by the developers when unit tests are being created
ATDD by the team to better define the requirements
A combination of TDD and BDD by the team to improve the pre-build testing

Correct answer: C

Explanation:

Acceptance Test-Driven Development (ATDD) involves the whole team collaboratively discussing acceptance criteria, with examples, and then distilling them into a set of concrete acceptance tests before development begins.It's a way to get clear on what to build, and it's done in a way that allows the team to know when a story is complete. ATDD helps to make sure that all the stakeholders have a common understanding of what is being built and what the success criteria are.Reference= The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of defining testable requirements within an Agile team and creating and implementing various Agile test approaches using appropriate techniques1.It also supports the contribution to test automation activities in an Agile project2, which aligns with the principles of ATDD.

Acceptance Test-Driven Development (ATDD) involves the whole team collaboratively discussing acceptance criteria, with examples, and then distilling them into a set of concrete acceptance tests before development begins.

It's a way to get clear on what to build, and it's done in a way that allows the team to know when a story is complete. ATDD helps to make sure that all the stakeholders have a common understanding of what is being built and what the success criteria are.

Reference= The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of defining testable requirements within an Agile team and creating and implementing various Agile test approaches using appropriate techniques1.It also supports the contribution to test automation activities in an Agile project2, which aligns with the principles of ATDD.

You have been working to define acceptance tests for a story. You think this will help tailor your testing. You have asked the product owner to be involved as well. You are currently looking at this story:

As a pet owner

I want to purchase food online

So that it can be delivered to my house when I need it

Which of the following is the preferred way to solicit information from the product owner to better understand what will be 'acceptable?

Propose the following acceptance criteria Purchase below the limit for free delivery Purchase above the limit for free delivery Request store pickup
Explain boundary value analysis to the product owner and have them indicate the appropriate boundaries to test
Work with the product owner to elicit examples of how they would use the software Combine their examples with testing techniques to flesh out the set of acceptance criteria
Create the following acceptance criteria and review them with the product owner Login Verify password reset Verify account details Update account details Browse and select food Add to cart Remove from cart Add moreitems to cart Select delivery Remove items from can until delivery is no longer free Checkout and verify the deliver charge is added Browse again and select food Select delivery and verify it is free Checkout and verify no delivery charge is added

Correct answer: C

Explanation:

Working with the product owner to elicit examples of usage is a key aspect of Agile methodologies. This collaborative approach ensures that the acceptance tests are relevant and based on real-world scenarios that reflect the product owner's vision. By combining these examples with testing techniques, testers can create a comprehensive set of acceptance criteria that are directly tied to the user's needs and the functionality of the software. This method aligns with the principles of Agile testing, where communication and collaboration are essential for understanding requirements and creating effective acceptance tests.

You are testing a large e-commerce system for household goods that is being implemented using Agile methodologies You are currently working on deriving tests tor stories that are implementing the following epic.

As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.

The story you are currently working on is

As a customer I want to be told how many items I need to purchase, so I can receive free shipping

Which of the following is an appropriate test charter for this story?

Login as a customer buy various goods request free delivery add more items to your cart checkout, verify that your delivery is free
Buy 12 of one item and see if you are advised that you get free shipping
Login as a customer buy an item verify message tells you how many are needed for free delivery add items to your cart until you qualify checkout verify delivery is free
As a supplier verify that when a customer purchases the correct number of goods the system doesn't add any delivery fees at checkout

Correct answer: C

Explanation:

The appropriate test charter for the user story provided should focus on the customer's experience and the functionality described in the story. Option C is the most suitable because it covers the entire process from the customer's perspective: logging in, purchasing an item, receiving information about the requirement for free shipping, adding more items, and then verifying that the delivery is free upon checkout. This test charter effectively tests the acceptance criteria of the user story by ensuring that the system provides the necessary information and applies the free shipping offer correctly when the conditions are met.

You are testing a large e-commerce system for household goods that is being implemented using Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.

As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.

The story you are currently working on is:

As a customer I want to be told when my items will be delivered, so I can plan to be home.

You have been given the following charter that was proposed by another tester for testing this story

Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.

What is the main flaw in this charter?

It focuses on the delivery company instead of the activities of the user
It does not cover the mam functionality of the user story
The expected results are not defined
The actions of the user are not clearly stated in the charter

Correct answer: B

Explanation:

The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.Reference= The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story's main functionality to ensure that tests provide adequate coverage12.It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story's objectives12.

The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.

Reference= The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story's main functionality to ensure that tests provide adequate coverage12.It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story's objectives12.

Consider the following section of pseudocode

Display 'You exceeded the number of tries to enter a password. Your account is now locked. Call customer.

For this section of code, which of the following issues should be identified during a code review?

1. Variables have not been properly defined with meaningful names

2. There are unused variables defined

3. Divisors are not tested for zero

4. Loop counters are not properly initialized

5. There are endless loops

6. There are statements within the loop that should be outside the loop

1, 3, 4, 5
7, 3, 4, 6
2, 3, 5, 6
1, 2, 4, 6

Correct answer: D

Explanation:

The pseudocode provided for review indicates a password entry system with a lockout mechanism after a certain number of failed attempts. The issues identified during the code review are:Variables have not been properly defined with meaningful names - the variables used in the pseudocode are not descriptive, which can make the code difficult to understand and maintain.There are unused variables defined - the pseudocode includes variables that are declared but not used, which is inefficient and can lead to confusion.Loop counters are not properly initialized - if a loop counter is used, it must be initialized correctly to ensure the loop functions as intended.There are statements within the loop that should be outside the loop - certain messages or actions may be repeated unnecessarily within a loop when they should be placed outside to execute only once.

The pseudocode provided for review indicates a password entry system with a lockout mechanism after a certain number of failed attempts. The issues identified during the code review are:

Variables have not been properly defined with meaningful names - the variables used in the pseudocode are not descriptive, which can make the code difficult to understand and maintain.

There are unused variables defined - the pseudocode includes variables that are declared but not used, which is inefficient and can lead to confusion.

Loop counters are not properly initialized - if a loop counter is used, it must be initialized correctly to ensure the loop functions as intended.

There are statements within the loop that should be outside the loop - certain messages or actions may be repeated unnecessarily within a loop when they should be placed outside to execute only once.